1 ECLIPSE ANDROID PROJECT IMPORT SUMMARY
2 ======================================
3
4 Ignored Files:
5 --------------
6 The following files were *not* copied
into the new Gradle project; you
7 should evaluate whether these are still needed
in your project and if
8 so manually move them:
9
10 * ic_launcher-web.png
11 * proguard-project.txt
12
13 Replaced Jars with Dependencies:
14 --------------------------------
15 The importer recognized the following .jar files
as third party
16 libraries and replaced them with Gradle dependencies instead. This has
17 the advantage that more
explicit version information is known, and the
18 libraries can be updated automatically. However, it
is possible that
19 the .jar file
in your project was of an older version than the
20 dependency we picked, which could render the project not compileable.
21 You can disable the jar replacement
in the import wizard and try again:
22
23 android-support-v4.jar => com.android.support:support-v4:
18.0.0
24
25 Moved Files:
26 ------------
27 Android Gradle projects use a different directory structure than ADT
28 Eclipse projects. Here
's how the projects were restructured:
29
30 * AndroidManifest.xml => app\src\main\AndroidManifest.xml
31 * assets\ => app\src\main\assets
32 * res\ => app\src\main\res\
33 * src\ => app\src\main\java\
34
35 Next Steps:
36 -----------
37 You can now build the project. The Gradle project needs network
38 connectivity to download dependencies.
39
40 Bugs:
41 -----
42 If
for some reason your project does not build, and you determine that
43 it
is due to a bug or limitation of the Eclipse to Gradle importer,
44 please file a bug at http:
//b.android.com with category
45 Component-Tools.
46
47 (This import summary
is for your information only, and can be deleted
48 after import once you are satisfied with the results.)


Gõ tìm kiếm nhanh...